home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: pete@borland.com (Pete Becker)
- Newsgroups: comp.lang.c++
- Subject: Re: COOL: Something you can do in "C" you can NOT do in "C++"
- Date: 16 Mar 1996 20:27:42 GMT
- Organization: Borland International
- Distribution: na
- Message-ID: <4if87u$rkm@druid.borland.com>
- References: <4hpov3$krb@qualcomm.com> <4i3123$etb@clarknet.clark.net> <4i4dep$bo1@lib104.its.rpi.edu>
- NNTP-Posting-Host: pbecker.borland.com
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=ISO-8859-1
- X-Newsreader: WinVN 0.99.5
-
- In article <4i4dep$bo1@lib104.its.rpi.edu>, floydb1@lib104.its.rpi.edu says...
- >
- >
- >In article <4i3123$etb@clarknet.clark.net>, gusty@clark.net (Harlan Messinger)
- writes:
- >|> Frank Merrow (fmerrow@wizard.qualcomm.com) wrote:
- >|> : Hi,
- >|> :
- >|> : I am teaching myself C++, but my interest in the language just dropped.
- >|> : I want to read cin as a binary file and output cout the same as well. I
- read
- >|> : the FAQs on C++ and guess what YOU CAN'T DO IT.
- >|> :
- >|>
- >|> Seeing as how C doesn't even _have_ cin or cout, I don't understand your
- >|> point.
- >
- >
- >Seems the point concerns 'binary' not 'cin/cout'. 'binary' i/o seems
- >to be system-specific. I vaguely recall reading something about
- >CR/LF interpretation on UNIX systems, where the CR/LF was not converted
- >in 'binary' i/o. Under MS-DOS 'binary' is something else.
-
- This is basically true in both C and C++. In both cases, the details of how the
- "binary" file is written are system dependent, but the meaning of operations on
- binary files is well defined and portable. The files themselves are not
- portable in either language.
-
-